mergify: add backport-v8.x always for main#40741
Merged
v1v merged 1 commit intoelastic:mainfrom Sep 10, 2024
Merged
Conversation
|
This pull request doesn't have a |
Contributor
Member
Author
I think there is one edge case: Someone can create a PR targeting $ gh pr create --label backport-skip --fill --base mainI assume that an edge case could happen, so I decided to raise this PR to play it safe. Therefore, any new PR targeting |
Contributor
|
Gotcha. Makes sense. Thanks for thinking of the edge case and creating this PR (and similar ones in other repos too)! |
ycombinator
approved these changes
Sep 10, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
Otherwise,
backport-skipor any otherbackport-labels could have higher precedence and thenbackport-v8.xwill not be attached.If
backport-8.xshould always be there for any PRs targetingmain, then this should help with.Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Disruptive User Impact
Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs